Choosing a concurrency model, optimistic or pessimistic
•
0 likes•1 view
This document discusses concurrency models and transactions in SQL Server. It describes two concurrency models: pessimistic and optimistic. Pessimistic concurrency uses locking to prevent conflicts while optimistic concurrency allows full access and detects conflicts. The document also covers SQL Server transactions and isolation levels, describing phenomena like lost updates, dirty reads and non-repeatable reads that different isolation levels allow or prevent.
Report
Share
Report
Share
![Why Study Concurrency? ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Break through e2e-testing
This document discusses breaking up end-to-end automation test cases into independent component-level test cases. It proposes using TestNG listeners to tie the component tests together and run them sequentially to still achieve end-to-end testing. Key benefits include increased independence, reliability, and ability to test specific components without rerunning the whole suite. Implementation would involve writing listener code to capture test data at each layer and passing it to the next as input using a data provider.
Choosing A Concurrency Model, Optimistic Or Pessimistic
This document discusses concurrency models and transaction handling in SQL Server. It covers optimistic and pessimistic concurrency approaches, and how SQL Server implements transactions using the ACID properties. Key concurrency issues like lost updates, dirty reads, and phantoms are explained. The document also discusses SQL Server's support for ANSI isolation levels and how it implements them using either pessimistic locking or new options like snapshot isolation in SQL Server 2005.
Testability: Factors and Strategy
Keynote, Google Test Automation Conference. Hyderabad, India, October 28, 2010.
Overview of software testability and implications for managers, developers, and testers. Discusses six aspects: process, requirements, design, white-box, black-box, and test tooling. Shows that testers are not typically in control of these aspects, which leads to sub-optimal software development outcomes.
SQL Server Transaction Management
Transactions are used to ensure data integrity and manage concurrent access in SQL Server. There are two types of transactions: implicit, which automatically commit after each statement, and explicit, which require BEGIN, COMMIT, or ROLLBACK statements. Transactions have ACID properties including atomicity, consistency, isolation, and durability. Isolation levels like read committed and serializable control how transactions see concurrent data modifications. Snapshot isolation is an alternative to locking that uses row versioning to provide consistency.
Unit testing solid fundamentals
This document discusses unit testing fundamentals. It defines a unit test as code that verifies the smallest testable part of an application. The key benefits of unit testing include enabling fast change and failure, creating executable specifications, and automating testing. Unit testing should start small and evolve over time using techniques like test-driven development (TDD). TDD involves writing tests before code in small iterative cycles from red to green to refactored. Test doubles like stubs, spies and mocks are used to isolate and control dependencies. While unit testing has limitations like time costs, it can help improve coding quality and catch errors. The document encourages starting unit testing on all new projects.
SELJE_Database_Unit_Testing_Slides.pdf
This document discusses database unit testing fundamentals. It defines unit testing as code that exercises specific portions of code to return a pass/fail result. The goals of unit testing are to catch mistakes early, ensure code works as expected, and maintain tight code. The document reviews how to unit test databases, using tSQLt and SQL Test frameworks. It provides examples of unit testing stored procedures, functions, views and constraints. Overall, the document promotes unit testing databases to write testable code and help prevent errors.
SQL Server 2012 Best Practices
This document provides SQL Server best practices for improving maintenance, performance, availability, and quality. It discusses generic best practices that are independent of SQL version as well as SQL Server 2012 specific practices. Generic best practices include coding standards, using Windows authentication, normalizing data, ensuring data integrity, cluster index design, and set-based querying. SQL Server 2012 specific practices cover AlwaysOn availability groups, columnstore indexes, contained databases, filetables, and how AlwaysOn compares to mirroring and clustering. The document emphasizes the importance of following best practices to take advantage of new SQL Server 2012 technologies and stresses considering data partitioning and the resource governor.
#DOAW16 - DevOps@work Roma 2016 - Testing your databases
In these slides we will speak about how to unit test our programmability in SQL Server and how to move from a manual process to an automated one in order to achieve the goals of DevOps
Recommended
Break through e2e-testing
This document discusses breaking up end-to-end automation test cases into independent component-level test cases. It proposes using TestNG listeners to tie the component tests together and run them sequentially to still achieve end-to-end testing. Key benefits include increased independence, reliability, and ability to test specific components without rerunning the whole suite. Implementation would involve writing listener code to capture test data at each layer and passing it to the next as input using a data provider.
Choosing A Concurrency Model, Optimistic Or Pessimistic
This document discusses concurrency models and transaction handling in SQL Server. It covers optimistic and pessimistic concurrency approaches, and how SQL Server implements transactions using the ACID properties. Key concurrency issues like lost updates, dirty reads, and phantoms are explained. The document also discusses SQL Server's support for ANSI isolation levels and how it implements them using either pessimistic locking or new options like snapshot isolation in SQL Server 2005.
Testability: Factors and Strategy
Keynote, Google Test Automation Conference. Hyderabad, India, October 28, 2010.
Overview of software testability and implications for managers, developers, and testers. Discusses six aspects: process, requirements, design, white-box, black-box, and test tooling. Shows that testers are not typically in control of these aspects, which leads to sub-optimal software development outcomes.
SQL Server Transaction Management
Transactions are used to ensure data integrity and manage concurrent access in SQL Server. There are two types of transactions: implicit, which automatically commit after each statement, and explicit, which require BEGIN, COMMIT, or ROLLBACK statements. Transactions have ACID properties including atomicity, consistency, isolation, and durability. Isolation levels like read committed and serializable control how transactions see concurrent data modifications. Snapshot isolation is an alternative to locking that uses row versioning to provide consistency.
Unit testing solid fundamentals
This document discusses unit testing fundamentals. It defines a unit test as code that verifies the smallest testable part of an application. The key benefits of unit testing include enabling fast change and failure, creating executable specifications, and automating testing. Unit testing should start small and evolve over time using techniques like test-driven development (TDD). TDD involves writing tests before code in small iterative cycles from red to green to refactored. Test doubles like stubs, spies and mocks are used to isolate and control dependencies. While unit testing has limitations like time costs, it can help improve coding quality and catch errors. The document encourages starting unit testing on all new projects.
SELJE_Database_Unit_Testing_Slides.pdf
This document discusses database unit testing fundamentals. It defines unit testing as code that exercises specific portions of code to return a pass/fail result. The goals of unit testing are to catch mistakes early, ensure code works as expected, and maintain tight code. The document reviews how to unit test databases, using tSQLt and SQL Test frameworks. It provides examples of unit testing stored procedures, functions, views and constraints. Overall, the document promotes unit testing databases to write testable code and help prevent errors.
SQL Server 2012 Best Practices
This document provides SQL Server best practices for improving maintenance, performance, availability, and quality. It discusses generic best practices that are independent of SQL version as well as SQL Server 2012 specific practices. Generic best practices include coding standards, using Windows authentication, normalizing data, ensuring data integrity, cluster index design, and set-based querying. SQL Server 2012 specific practices cover AlwaysOn availability groups, columnstore indexes, contained databases, filetables, and how AlwaysOn compares to mirroring and clustering. The document emphasizes the importance of following best practices to take advantage of new SQL Server 2012 technologies and stresses considering data partitioning and the resource governor.
#DOAW16 - DevOps@work Roma 2016 - Testing your databases
In these slides we will speak about how to unit test our programmability in SQL Server and how to move from a manual process to an automated one in order to achieve the goals of DevOps
Database concurrency and transactions - Tal Olier
This document provides an overview of database transactions and locking concepts. It discusses the ACID model which guarantees atomicity, consistency, isolation, and durability. It describes different isolation levels and how they handle phenomena like dirty reads. It also covers locking types including exclusive and share locks. Advanced topics covered include concurrency, lock escalation, and how transactions and locking are implemented differently in Oracle and SQL Server.
SQL Server Transaction Management
This presentation explains how transactions are managed in SQL Server and walks through the various isolation levels that are available.
Getting Started With Testing
This document provides an overview of testing concepts and best practices. It discusses different types of bugs, the benefits of writing unit tests, test types like unit tests and integration tests, testability factors, isolation techniques using test doubles, common mistakes to avoid, and Microsoft Fakes for improving testability. The key points covered are:
- The importance of writing tests to prevent bugs and allow safe refactoring.
- Techniques like dependency injection, interfaces, and seams to make code more testable and allow isolation using stubs, fakes, mocks, and shims.
- Common mistakes for test code like testing multiple features in one test, long test runs without maintenance, lack of negative testing, and unclear
Clean & Dirty Acceptance Tests with Cucumber & Watir
The document discusses different levels of automated testing including unit tests, system integration tests, acceptance criteria tests, and regression testing. It then covers disadvantages of UI automation using Selenium or Watir like brittle tests, time consuming writing and maintenance, and slow execution. Ways to minimize these disadvantages include reducing test numbers, decoupling tests from data, and reducing writing/modification time. The remainder discusses approaches to exploratory testing with Cucumber including writing quick dirty tests and separating clean from dirty code.
Fantastic Tests - The Crimes of Bad Test Design
The document discusses why testing is important and what causes bad tests. Testing provides comfort and confidence by knowing if new code breaks existing functionality. Bad tests have a wide scope so it's unclear what they test, depend on specific orders or system states, are too similar to the product without the same fragility, or are not similar enough to the user experience. The key is for tests to be independent of order or system state and balance similarity to the product with enough differences to reliably fail when bugs are present.
TDD Best Practices
Ever tried doing Test First Test Driven Development? Ever failed? TDD is not easy to get right. Here's some practical advice on doing BDD and TDD correctly. This presentation attempts to explain to you why, what, and how you should test, tell you about the FIRST principles of tests, the connections of unit testing and the SOLID principles, writing testable code, test doubles, the AAA of unit testing, and some practical ideas about structuring tests.
Sql server infernals
Let’s face it: Best Practices are too many to really know them all and choose which ones should be applied first. Does your telephone ring all the time? Do your users ask for that “quick report” that instead takes ages and keeps changing every time you think it’s done? Have you ever thought that in dire times avoiding Worst Practices could be a good starting point and you can leave fine tuning for a better future? If the answer is “yes”, then this session is for you: we will discover together how not to torture a SQL Server instance and we will see how to avoid making choices that in the long run could turn out to be not as smart as they looked initially.
Shift-Left Testing: QA in a DevOps World by David Laulusa
Shift-left testing involves injecting quality earlier in the software development process through techniques like unit testing, test-driven development, and regression testing. The presentation discusses principles for effective testing including equivalence partitioning, boundary value analysis, and combinatorial testing. It emphasizes the importance of collaboration between testers and developers through practices like dependency injection and test automation.
Tdd in android (mvp)
This document discusses test-driven development (TDD) in Android and provides examples of how to apply TDD principles. It explains what TDD is and the typical "red-green-refactor" process. It also notes some challenges of TDD in Android, such as difficulty mocking Android components. The document advocates separating an app into layers (e.g. view, presenter, model) to enable individual testing and provides a demo of how to structure an app with login functionality into testable layers. Finally, it outlines some benefits of TDD like faster feedback, better design, and confidence during refactoring.
Test Driven Development (TDD)
This document provides an overview of test-driven development (TDD). TDD involves writing tests before writing code to ensure new functionality works as intended. Key principles of TDD include writing failing tests first, then code to pass the tests, and refactoring code while maintaining all tests. TDD results in higher quality, flexible, readable and maintainable code. It also helps improve both internal code quality and external functionality through a well-designed development process focused on automated testing.
6 Traits of a Successful Test Automation Architecture
This document discusses 6 traits of a successful test automation architecture:
1. Deciding which test levels to automate by considering factors like efficiency, expected vs unexpected scenarios, and intelligence vs repetitiveness.
2. Design principles for test automation including modularity, reusability, and separation of concerns.
3. Locator strategy which determines whether tests are flaky or robust, prioritizing unique, descriptive locators that are unlikely to change.
4. Methodology such as behavior driven development, test driven development, and continuous testing approaches.
5. Framework and language selection considering project dynamics and technologies. Examples mentioned are Geb, Spock, Groovy, and CodeceptJS.
6.
How Not to be a Cranky DBA
This document provides Mike Hillwig's top 10 rules for managing a production SQL Server environment and avoiding becoming a "cranky DBA". The rules include: don't enable auto shrink; triggers shouldn't send mail directly but use a queue table instead; developers should not touch production; master the SQL Agent; use instant file initialization; test restores frequently; set min and max RAM; limit access to SA and service accounts; and keep database servers dedicated only to databases. The overall message is that following best practices helps avoid unnecessary issues that cause stress and make DBAs cranky.
Clean Unit Test Patterns
Slides of my talk at GDG DevFestKarlsruhe 2014 about the fundamentals of how to write clean unit tests.
Clean code
This document discusses principles and best practices for writing clean code. It defines clean code as code that works, is easy to read, understand and extend. It emphasizes writing code for other developers who will maintain it. Some key points include writing small, focused methods with meaningful names; avoiding duplicated code; using exceptions appropriately; formatting code consistently; and writing thorough automated tests. The overall goal is to communicate intent in the code as clearly as possible through these practices.
Acceptance Test Driven Development at StarWest 2014
This is my half day Acceptance Test Driven Development course as given in Anaheim at StarWest 2014 (October). It's based on Ken Pugh's 1/2 day tutorial.
No More No Repro
Microsoft's Visual Studio 2010 and Team Foundation Server 2010 include many new and improved testing capabilities that aim to break down silos between development and testing teams. Key features include innovative test case management, automated build-deploy-test workflows, test lab management for virtual environments, rich bug filing capabilities, and tools to help developers identify and fix issues early like IntelliTrace and Coded UI testing. The integrated offerings are designed to align quality assurance more closely with the development lifecycle and enable highly leveraged QA teams.
AWS Summit Melbourne 2014 | The Path to Business Agility for Vodafone: How Am...
As part of Vodafone Hutchison Australia (VHA)’s company-wide mission to win back customers, the VHA Digital Products division, with the help of DiUS, built a strategic internal agile development and innovation capability. By leveraging AWS, VHA now has the powerful ability to be more responsive, to experiment, fail-fast and in turn, to deliver an improved customer experience across all digital touchpoints.
We will share VHA’s journey so far by looking at the business objectives and diving into how people, process and technology made it happen:
Making a business case for AWS
Working within a complex technology landscape including legacy systems, COTS products as well as custom-built systems
The role AWS played in achieving change
Enabling daily deployments using Continuous Delivery and other practices and tools
What's next on VHA's agility roadmap
Presenters: Andy McCarthy, Digital Technology Manager, Vodafone Hutchison Australia, & Elliot Murry, Senior Consultant, DiUS
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
Roy Osherove provides training courses on topics like test-driven development (TDD), behavior-driven development (BDD), and consulting/coaching services. He discusses test reviews as an alternative to code reviews that can be quicker and help learning teams. The presentation focuses on creating tests that are trustworthy, maintainable, and readable through techniques like avoiding test logic, not repeating production logic, separating unit and integration tests, and using readable structures, naming, and avoiding magic values.
How not to be a cranky dba
The document provides tips from Mike Hillwig on how to avoid being a cranky DBA. Some key tips include: avoiding the use of auto shrink on databases as it can fragment indexes; using SQL Agent to automate manual tasks; setting minimum and maximum RAM on servers; testing restores frequently; and limiting access to SA and service accounts. The document stresses the importance of consistency across environments for easier troubleshooting and remembering configurations. It also recommends databases servers be dedicated solely to database operations.
TDD - survival guide
The document provides an overview of test-driven development (TDD), including:
1. TDD follows a basic workflow of writing a failing test first, then code to pass the test, and refactoring.
2. TDD is not a replacement for high-level design or frameworks, as it is bottom-up and doesn't provide a big picture view.
3. Unit tests are a tool used in TDD to drive design and ensure correctness, but other types of tests are also needed.
Backup beyond just a strategy with SQL Server
This document discusses strategies for effective SQL Server backups. It covers the phases of restore including file creation, data/log copying, redo, and undo. It discusses ways to optimize restore speed such as skipping zero initialization, hardware configuration tuning, and backup frequency. It also covers piecemeal restores of files/filegroups to maintain partial database availability and techniques for simple recovery model databases.
SQL Server Query Optimization, Execution and Debugging Query Performance
This document summarizes a presentation on SQL Server query optimization, execution, and debugging query performance. The key takeaways are: 1) estimated row counts affect plan selection because the optimizer uses cardinality estimates to determine query plan costs; 2) tools like SSMS, DMVs, and tracing can be used to find estimated and actual row counts and compare query plans; 3) parameterized queries can cause issues if the plan is reused for parameter values that expected different plans. Techniques for influencing plan choice and testing considerations for parameterized queries are also discussed.
More Related Content
Similar to Choosing a concurrency model, optimistic or pessimistic
Database concurrency and transactions - Tal Olier
This document provides an overview of database transactions and locking concepts. It discusses the ACID model which guarantees atomicity, consistency, isolation, and durability. It describes different isolation levels and how they handle phenomena like dirty reads. It also covers locking types including exclusive and share locks. Advanced topics covered include concurrency, lock escalation, and how transactions and locking are implemented differently in Oracle and SQL Server.
SQL Server Transaction Management
This presentation explains how transactions are managed in SQL Server and walks through the various isolation levels that are available.
Getting Started With Testing
This document provides an overview of testing concepts and best practices. It discusses different types of bugs, the benefits of writing unit tests, test types like unit tests and integration tests, testability factors, isolation techniques using test doubles, common mistakes to avoid, and Microsoft Fakes for improving testability. The key points covered are:
- The importance of writing tests to prevent bugs and allow safe refactoring.
- Techniques like dependency injection, interfaces, and seams to make code more testable and allow isolation using stubs, fakes, mocks, and shims.
- Common mistakes for test code like testing multiple features in one test, long test runs without maintenance, lack of negative testing, and unclear
Clean & Dirty Acceptance Tests with Cucumber & Watir
The document discusses different levels of automated testing including unit tests, system integration tests, acceptance criteria tests, and regression testing. It then covers disadvantages of UI automation using Selenium or Watir like brittle tests, time consuming writing and maintenance, and slow execution. Ways to minimize these disadvantages include reducing test numbers, decoupling tests from data, and reducing writing/modification time. The remainder discusses approaches to exploratory testing with Cucumber including writing quick dirty tests and separating clean from dirty code.
Fantastic Tests - The Crimes of Bad Test Design
The document discusses why testing is important and what causes bad tests. Testing provides comfort and confidence by knowing if new code breaks existing functionality. Bad tests have a wide scope so it's unclear what they test, depend on specific orders or system states, are too similar to the product without the same fragility, or are not similar enough to the user experience. The key is for tests to be independent of order or system state and balance similarity to the product with enough differences to reliably fail when bugs are present.
TDD Best Practices
Ever tried doing Test First Test Driven Development? Ever failed? TDD is not easy to get right. Here's some practical advice on doing BDD and TDD correctly. This presentation attempts to explain to you why, what, and how you should test, tell you about the FIRST principles of tests, the connections of unit testing and the SOLID principles, writing testable code, test doubles, the AAA of unit testing, and some practical ideas about structuring tests.
Sql server infernals
Let’s face it: Best Practices are too many to really know them all and choose which ones should be applied first. Does your telephone ring all the time? Do your users ask for that “quick report” that instead takes ages and keeps changing every time you think it’s done? Have you ever thought that in dire times avoiding Worst Practices could be a good starting point and you can leave fine tuning for a better future? If the answer is “yes”, then this session is for you: we will discover together how not to torture a SQL Server instance and we will see how to avoid making choices that in the long run could turn out to be not as smart as they looked initially.
Shift-Left Testing: QA in a DevOps World by David Laulusa
Shift-left testing involves injecting quality earlier in the software development process through techniques like unit testing, test-driven development, and regression testing. The presentation discusses principles for effective testing including equivalence partitioning, boundary value analysis, and combinatorial testing. It emphasizes the importance of collaboration between testers and developers through practices like dependency injection and test automation.
Tdd in android (mvp)
This document discusses test-driven development (TDD) in Android and provides examples of how to apply TDD principles. It explains what TDD is and the typical "red-green-refactor" process. It also notes some challenges of TDD in Android, such as difficulty mocking Android components. The document advocates separating an app into layers (e.g. view, presenter, model) to enable individual testing and provides a demo of how to structure an app with login functionality into testable layers. Finally, it outlines some benefits of TDD like faster feedback, better design, and confidence during refactoring.
Test Driven Development (TDD)
This document provides an overview of test-driven development (TDD). TDD involves writing tests before writing code to ensure new functionality works as intended. Key principles of TDD include writing failing tests first, then code to pass the tests, and refactoring code while maintaining all tests. TDD results in higher quality, flexible, readable and maintainable code. It also helps improve both internal code quality and external functionality through a well-designed development process focused on automated testing.
6 Traits of a Successful Test Automation Architecture
This document discusses 6 traits of a successful test automation architecture:
1. Deciding which test levels to automate by considering factors like efficiency, expected vs unexpected scenarios, and intelligence vs repetitiveness.
2. Design principles for test automation including modularity, reusability, and separation of concerns.
3. Locator strategy which determines whether tests are flaky or robust, prioritizing unique, descriptive locators that are unlikely to change.
4. Methodology such as behavior driven development, test driven development, and continuous testing approaches.
5. Framework and language selection considering project dynamics and technologies. Examples mentioned are Geb, Spock, Groovy, and CodeceptJS.
6.
How Not to be a Cranky DBA
This document provides Mike Hillwig's top 10 rules for managing a production SQL Server environment and avoiding becoming a "cranky DBA". The rules include: don't enable auto shrink; triggers shouldn't send mail directly but use a queue table instead; developers should not touch production; master the SQL Agent; use instant file initialization; test restores frequently; set min and max RAM; limit access to SA and service accounts; and keep database servers dedicated only to databases. The overall message is that following best practices helps avoid unnecessary issues that cause stress and make DBAs cranky.
Clean Unit Test Patterns
Slides of my talk at GDG DevFestKarlsruhe 2014 about the fundamentals of how to write clean unit tests.
Clean code
This document discusses principles and best practices for writing clean code. It defines clean code as code that works, is easy to read, understand and extend. It emphasizes writing code for other developers who will maintain it. Some key points include writing small, focused methods with meaningful names; avoiding duplicated code; using exceptions appropriately; formatting code consistently; and writing thorough automated tests. The overall goal is to communicate intent in the code as clearly as possible through these practices.
Acceptance Test Driven Development at StarWest 2014
This is my half day Acceptance Test Driven Development course as given in Anaheim at StarWest 2014 (October). It's based on Ken Pugh's 1/2 day tutorial.
No More No Repro
Microsoft's Visual Studio 2010 and Team Foundation Server 2010 include many new and improved testing capabilities that aim to break down silos between development and testing teams. Key features include innovative test case management, automated build-deploy-test workflows, test lab management for virtual environments, rich bug filing capabilities, and tools to help developers identify and fix issues early like IntelliTrace and Coded UI testing. The integrated offerings are designed to align quality assurance more closely with the development lifecycle and enable highly leveraged QA teams.
AWS Summit Melbourne 2014 | The Path to Business Agility for Vodafone: How Am...
As part of Vodafone Hutchison Australia (VHA)’s company-wide mission to win back customers, the VHA Digital Products division, with the help of DiUS, built a strategic internal agile development and innovation capability. By leveraging AWS, VHA now has the powerful ability to be more responsive, to experiment, fail-fast and in turn, to deliver an improved customer experience across all digital touchpoints.
We will share VHA’s journey so far by looking at the business objectives and diving into how people, process and technology made it happen:
Making a business case for AWS
Working within a complex technology landscape including legacy systems, COTS products as well as custom-built systems
The role AWS played in achieving change
Enabling daily deployments using Continuous Delivery and other practices and tools
What's next on VHA's agility roadmap
Presenters: Andy McCarthy, Digital Technology Manager, Vodafone Hutchison Australia, & Elliot Murry, Senior Consultant, DiUS
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
Roy Osherove provides training courses on topics like test-driven development (TDD), behavior-driven development (BDD), and consulting/coaching services. He discusses test reviews as an alternative to code reviews that can be quicker and help learning teams. The presentation focuses on creating tests that are trustworthy, maintainable, and readable through techniques like avoiding test logic, not repeating production logic, separating unit and integration tests, and using readable structures, naming, and avoiding magic values.
How not to be a cranky dba
The document provides tips from Mike Hillwig on how to avoid being a cranky DBA. Some key tips include: avoiding the use of auto shrink on databases as it can fragment indexes; using SQL Agent to automate manual tasks; setting minimum and maximum RAM on servers; testing restores frequently; and limiting access to SA and service accounts. The document stresses the importance of consistency across environments for easier troubleshooting and remembering configurations. It also recommends databases servers be dedicated solely to database operations.
TDD - survival guide
The document provides an overview of test-driven development (TDD), including:
1. TDD follows a basic workflow of writing a failing test first, then code to pass the test, and refactoring.
2. TDD is not a replacement for high-level design or frameworks, as it is bottom-up and doesn't provide a big picture view.
3. Unit tests are a tool used in TDD to drive design and ensure correctness, but other types of tests are also needed.
Similar to Choosing a concurrency model, optimistic or pessimistic (20)
Clean & Dirty Acceptance Tests with Cucumber & Watir
Clean & Dirty Acceptance Tests with Cucumber & Watir
Shift-Left Testing: QA in a DevOps World by David Laulusa
Shift-Left Testing: QA in a DevOps World by David Laulusa
6 Traits of a Successful Test Automation Architecture
6 Traits of a Successful Test Automation Architecture
Acceptance Test Driven Development at StarWest 2014
Acceptance Test Driven Development at StarWest 2014
AWS Summit Melbourne 2014 | The Path to Business Agility for Vodafone: How Am...
AWS Summit Melbourne 2014 | The Path to Business Agility for Vodafone: How Am...
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
Roy Osherove on Unit Testing Good Practices and Horrible Mistakes
More from Vinod Kumar
Backup beyond just a strategy with SQL Server
This document discusses strategies for effective SQL Server backups. It covers the phases of restore including file creation, data/log copying, redo, and undo. It discusses ways to optimize restore speed such as skipping zero initialization, hardware configuration tuning, and backup frequency. It also covers piecemeal restores of files/filegroups to maintain partial database availability and techniques for simple recovery model databases.
SQL Server Query Optimization, Execution and Debugging Query Performance
This document summarizes a presentation on SQL Server query optimization, execution, and debugging query performance. The key takeaways are: 1) estimated row counts affect plan selection because the optimizer uses cardinality estimates to determine query plan costs; 2) tools like SSMS, DMVs, and tracing can be used to find estimated and actual row counts and compare query plans; 3) parameterized queries can cause issues if the plan is reused for parameter values that expected different plans. Techniques for influencing plan choice and testing considerations for parameterized queries are also discussed.
Advanced t sql - querying and programming inside sql server
This document summarizes an upcoming session on advanced Transact-SQL querying and programming techniques in SQL Server. The session objectives are to demonstrate interesting feature usages and explore SQL Server through examples. The agenda includes introductions, T-SQL enhancements in SQL Server 2008, techniques, tips and tricks with a focus on demonstration through code examples. The summary encourages attendees to keep exploring new SQL Server features and ways of working with the database for a fun learning experience.
Sql Server Security
SQL Server 2005 introduced enhancements to security including:
1. Authentication can specify SSL or mutual authentication with client certificates. Authorization establishes login credentials and permissions within a database.
2. A new security model separates users from schemas, allowing dropping a user without breaking applications. Users have a default schema and objects are contained within schemas.
3. Cryptography support provides encryption, decryption, signing and verification functions including symmetric and asymmetric keys. Permissions in SQL 2005 allow finer-grained control at the row level and module execution context.
Windows Mobile 5.0 Data Access And Storage Webcast
Windows Mobile has been updated with several new features for data access and storage. SQL Mobile now supports multi-user access to databases, an improved query processor, and administration of databases from a desktop. A new SqlCeResultSet provides a scrollable, updatable cursor for direct data access with performance similar to SqlCeDataReader. The DataSet provides new methods for serialization, copying data, getting changes, and merging data to improve synchronization capabilities. Additional XML support through classes like XmlSerializer, XPath, and XmlSchema bring greater capabilities. Tools have been added for managing device databases from the desktop in Visual Studio.
Protecting Your Key Asset – Data Protection Best Practices V2.0 Final
The document discusses various data protection best practices, including using encryption techniques like Encrypting File System (EFS) and Windows Rights Management Services (RMS) to secure files and data on devices. It also covers database security practices like implementing proper permissions on SQL Server principals and securables. The key recommendations are to use all available security controls including technology, processes and people, practice defense in depth, and reduce potential vulnerabilities.
More from Vinod Kumar (6)
SQL Server Query Optimization, Execution and Debugging Query Performance
SQL Server Query Optimization, Execution and Debugging Query Performance
Advanced t sql - querying and programming inside sql server
Advanced t sql - querying and programming inside sql server
Windows Mobile 5.0 Data Access And Storage Webcast
Windows Mobile 5.0 Data Access And Storage Webcast
Protecting Your Key Asset – Data Protection Best Practices V2.0 Final
Protecting Your Key Asset – Data Protection Best Practices V2.0 Final
Recently uploaded
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
UiPath Test Automation using UiPath Test Suite series, part 5
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
20 Comprehensive Checklist of Designing and Developing a Website
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Recently uploaded (20)
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
UiPath Test Automation using UiPath Test Suite series, part 5
UiPath Test Automation using UiPath Test Suite series, part 5
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
Choosing a concurrency model, optimistic or pessimistic
- 1. Choosing a Concurrency Model Optimistic or Pessimistic with SQL Server Vinod Kumar M Technology Evangelist – Microsoft www.ExtremeExperts.com 20 / 04 / 10
- 12. SQL 2008 Isolation Levels Phenomena Allowed Isolation Levels Dirty Read Non-Repeatable Read Phantoms Update Conflict Concurrency Model READ UNCOMMITTED Yes Yes Yes No READ COMMITTED 1 Locking 2 Snapshot No No Yes Yes Yes Yes No No Pessimistic Optimistic REPEATABLE READ No No Yes No Pessimistic SNAPSHOT No No No Yes Optimistic SERIALIZABLE No No No No Pessimistic
- 13. Locking Decision Isolation level Scan type (Range, Table, Probe) # of rows in scan # of rows/page Locking strategy (Table, Page, Row) Operation type (scan, update) Current Activity Lock hints sp_IndexOption Settings
- 14. Walk through ISOLATION Levels